Skip to content

Cherry pick PR #9367: Remove freeze event and add flags to reduce background throttling#10038

Draft
cobalt-github-releaser-bot wants to merge 1 commit intomainfrom
cherry-pick-main-9367
Draft

Cherry pick PR #9367: Remove freeze event and add flags to reduce background throttling#10038
cobalt-github-releaser-bot wants to merge 1 commit intomainfrom
cherry-pick-main-9367

Conversation

@cobalt-github-releaser-bot
Copy link
Copy Markdown
Collaborator

Refer to the original PR: #9367

Removing freeze will allow visibilityChange events to be processed
even for async functions like storage flushing or XHRs.

This will also allow web app to execute for some time after backgrounded.

Note that this does not bring c26 to parity with c25 in terms of
life cycle changes.

Bug: 489533179
Bug: 488071716

)

Removing freeze will allow visibilityChange events to be processed
even for async functions like storage flushing or XHRs.

This will also allow web app to execute for some time after
backgrounded.

Note that this does not bring c26 to parity with c25 in terms of
life cycle changes.

Bug: 489533179
Bug: 488071716
(cherry picked from commit 6203f67)
@cobalt-github-releaser-bot
Copy link
Copy Markdown
Collaborator Author

MERGE CONFLICT CAT

Caution

There were merge conflicts while cherry picking! Check out cherry-pick-main-9367 and fix the conflicts before proceeding. Check the log at https://github.com/youtube/cobalt/actions/runs/24424827563 for details.

@github-actions
Copy link
Copy Markdown
Contributor

🤖 Gemini Suggested Commit Message


cobalt: Disable freeze event; add background flags

Disable the document.onfreeze event by default. This change allows web
applications to continue processing visibilityChange events and execute
async functions, such as storage flushing or XHRs, for some time after
being backgrounded.

Introduce new Java flags, including --disable-renderer-backgrounding,
--disable-features=StopInBackground, and
--disable-features=IntensiveWakeUpThrottling, to reduce background
throttling and allow explicit re-enabling of the freeze event.

Bug: 489533179
Bug: 488071716

💡 Pro Tips for a Better Commit Message:

  1. Influence the Result: Want to change the output? You can write custom prompts or instructions directly in the Pull Request description. The model uses that text to generate the message.
  2. Re-run the Generator: Post a comment with: /generate-commit-message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants